Systems and methods for providing clustered health checks

ABSTRACT

Systems and methods for providing clustered health checks are described herein. The systems and methods enable a user to select one or more selectable links to group together. The selectable links are associated with computing resources used by an application. Once selected, a parallel executor server receives the links and issues a health check command code to the computing resources associated with the group. The computing resources can be grouped together based on various reasons. The selectable links can be rendered in a graphical user interface of a health check application or an Internet browser.

BACKGROUND

Modern applications are typically designed in a way that thefunctionality provided to the application is scaled across variousservers and/or data stores. To maintain the functionality, and to reducethe probability that customers would have their service interrupted, thestatus of the various servers and/or data stores is often checked on aregular basis. In some conventional systems, the applicationdesigners/engineers, after deploying the application on multiple serversand/or data stores, test the servers and/or data stores to ensure thatthe “health” of the servers and/or data stores are sufficient beforeclosing the development cycle. In modern systems, applications can bescaled across hundreds or thousands of nodes, therefore making itdifficult to check the status of one or more of the servers and/or datastores.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth with reference to the accompanyingfigures. In the figures, the left-most digit(s) of a reference numberidentifies the figure in which the reference number first appears. Theuse of the same reference numbers in different figures indicates similaror identical items or features.

FIG. 1 depicts a system for providing clustered health checks, inaccordance with some examples of the present disclosure.

FIG. 2 is an illustration of a browser integrated with a health checkapplication rendered on a user equipment that may be used for providingclustered health checks, in accordance with some examples of the presentdisclosure.

FIG. 3 is an illustrative process for establishing identifiers toprovide clustered health checks, in accordance with some examples of thepresent disclosure.

FIG. 4 is an illustrative process for using a health check application,in accordance with some examples of the present disclosure.

FIG. 5 is an illustrative process for executing a health check commandby a parallel executor server, in accordance with some examples of thepresent disclosure.

FIG. 6 depicts a component level view of a user equipment for use withthe systems and methods described herein.

DETAILED DESCRIPTION

Examples of the present disclosure can comprise systems and methods forproviding clustered health checks. In some examples, the “health,” orfunctional status, of various servers, data stores, and other computerresources used by an application to provide functionality for theapplication can be checked using a collection and grouping userinterface in a browser or other application. When instantiated for useby the application, a computing resource used by the application isassigned an identifier, such as a uniform resource locator (URL).

The identifier assigned to the computing resource is stored in a list inan identifier datastore. The list is provided to a user, such as anengineer or developer of the application, for initializing a healthcheck. The one or more URLs of the computing resources can be stored,for example, as bookmarks in a browser. The user can select the bookmarkand the health check is commenced on the computing resource associatedwith the URL of the selected bookmark.

In some examples, the identifier can be grouped automatically or by theuser to perform a specific health check. For example, the identifiers ofall data stores can be grouped together under one identifier and theidentifiers for all servers can be grouped together under anotheridentifier. Thus, instead of selecting all the identifiers for the datastores (or having to remember the identifiers for all the data stores),a single identifier may be selected. Once selected, the identifierinitiates a group health check of all the identifiers associated withthe selected identifier.

The identifiers can be grouped together for other reasons. A user mayknow that one or more servers/data stores/computing resources arecritical for the application. For example, a computing resource may begeographically closest to users that use the application. Because of thegeographic proximity of the computing resource to the users that use theapplication, the use of the computing resource may help reduce latencyover other computing resources that are geographically more distant. Theidentifiers of computing resources that help reduce latency may begrouped under a single identifier. Health checks can be specified tooccur on a more regular basis for these specific computing resourcesbecause of their critical nature. Further, the health checks of thesecritical computing resources can be readily differentiated from healthchecks of other, potentially non-critical resources simply by groupingidentifiers.

Some examples of the presently disclosed subject matter may help reducecosts, increase efficiency, and reduce human error. In some conventionalsystems, the amount of time that may be required for humans to find theright computing resources and perform health checks can be timeconsuming. Further, the selection process can introduce errors, as thehuman may not know the correct computing resource or incorrectly selecta wrong computing resource upon which a health check is to be performed.

The systems and methods discussed herein are discussed generally withrespect to cellular UEs, tablets, computers, and the like, and in termsof components (e.g., network entities) associated with Wi-Fi networks,Bluetooth networks, wired networks, fourth-generation (4G) andfifth-generation (5G) cellular networks, and other types of networks.The systems and methods can be used with other types of equipment and onother types of networks. Thus, the systems and methods described hereinare described in terms of the 4G and 5G networks merely because thesenetworks represent the state of the current art. One of skill in the artwill recognize, however, the systems and methods could also be used onother networks that provide video calling such as, for example, Internetof Things (IoT), machine-to-machine (M2M), sixth-generation (6G), andother current and future networks.

As shown in FIG. 1, examples of the present disclosure can comprise asystem 100 for providing clustered health checks. The system 100includes a user equipment (UE) 102 running a health check application104. The UE 102 may be associated with the monitoring and/or maintenanceof computing resources. The health check application 104 is configuredto perform multiple operations, but, is generally designed to providefor the grouping of identifiers of various computing resources used foran application 106 to be run on a user's user equipment (UE) 108. Thehealth check application 104 receives information such as whichcomputing resources 110A-110N (hereinafter collectively referred to as“the computing resources 110” and individually as “the computingresource 110A,” the computing resource 110B,” and so forth) are to beused by the application 106. For example, the application 106 may needthe computing resource 110A and the computing resource 110B to beservers to host various aspects of the application 106. Further, theapplication 106 may use the computing resource 110N as a data store tostore data associated with the use of the application 106.

The health check application 104 queries the computing resources 110A,110B, and 110N after being identified as computing resources 110associated with the use of the application 106, and, queries theassociated computing resources 110 for an identifier associated with theassociated computing resources 110. In some examples, the identifier maybe a uniform resource locator (URL) associated with the computingresources 110. Other types of identifiers may be used and are consideredto be within the scope of the presently disclosed subject matterincluding, but not limited to, an Internet Protocol (IP) address, a nodeaddress in the case of a node, or any other information that may be usedto find and access the particular computing resources 110. It should benoted that in some examples, however, the identifiers may be generatedat the runtime of the health check application 104, such as when theapplication 106 is being executed.

Once the identifier is received, the health check application 104 storesthe identifiers in a data store 112. It should be noted that theidentifiers may be stored in other storage locations, the data store 112merely being an example. To store the identifiers, the health checkapplication 104 communicates with a parallel executor server 114. Theparallel executor server 114 receives the identifiers from the computingresources 110. Further, the health parallel executor server 114associates health check commands with the identifiers stored in the datastore 112, described in more detail in the following figures. Using theapplication 106, the UE 108 can be in communication with a cellularwireless base station (WBS) 116. The WBS 116, along with various othernetwork systems (not illustrated) can provide the UE 108 with a cellularvoice and/or data connection to the World Wide Web 118. The computingresources 110 can be accessed by the application 106 using the WorldWide Web 118, or other communication services.

Returning to the parallel executor server 114, once the identifiers arereceived and stored in the data store 112, the identifiers areassociated with a health check identifier and a command string. Thehealth check identifier is used to communicate with the parallelexecutor server 114 rather than the computing resources 110. The commandstring is used to initiate a health check using a health check commandcode on the computing resource 110 associated with the identifier whenthe identifier is selected. For example, as described in more detail inFIG. 2, the identifier may be a URL associated with the computingresource 110A. A health check URL may be stored in the data store 112.The health check URL may be provided to the health check application 104and/or directly to another application such as an Internet browser. Thehealth check URL may be entered into an address bar of the browser. Oncethe parallel executor server 114 receives the health check URL, theparallel executor server 114 sends a health check command code (orhealth check command) to the URL associated with the health check URL.The health check information is transmitted to the parallel executorserver 114, and in turn, provided to the health check application 104 oranother application like a browser.

In some examples, more than one URL of the computing resources may beassociated with one health check URL. In that regard, entering onehealth check URL in the address bar of a browser or other applicationmay initiate health checks on multiple computing resources 110 groupedinto the single health check URL. Once the single health check URL isreceived by the parallel executor server 114, the parallel executorserver 114 determines the URLs of the computing resources 110 associatedwith the grouped, single URL. The parallel executor server 114 transmitsa health check command code to the computing resources 110 associatedwith the grouped URL. Once the health check information is received fromthe computing resources 110, the health check information is provided tothe UE 102.

FIG. 2 is an illustration of a browser 202 integrated with the healthcheck application 104 rendered on the user equipment 102 that may beused for providing clustered health checks. The browser 202 includes anaddress bar 204 configured to receive a URL 206. The URL 206 isassociated with one or more of the computing resources 110 illustratedin FIG. 1, above. The URL 206 may be provided in a bookmarks bar 208.

The bookmarks bar 208 is a listing of URLs 206 that may be used toperform health checks on one or more applications. The bookmarks bar 208may indicate the URLs 206 (hereinafter collectively referred to as “URLs206” and individually as “URL 206A,” the URL 206B,” and so forth) indifferent manners to indicate the association with differentapplications. For example, URLs 206A, 206B, and 206D may be associatedwith the computing resources 110 used by the application 106. Displayedin a different manner, URL 206D may be associated with anotherapplication.

Once entered, the URL 206 entered in the address bar 204 is received bythe parallel executor server 114. The parallel executor server 114determines the URLs of the computing resources 110 associated with URL206. The parallel executor server 114 transmits a health check commandcode to the computing resources 110 associated with the URL 206. Oncethe health check information is received from the computing resources110, the health check information is provided to the UE 102 and renderedin the health check status user interface 212. The health check statususer interface 212 can include an identification of the computingresources 110 upon which a health check was performed, health checkinformation of the computing resources 110, and a status of thecomputing resources 110.

As noted above, the URLs 206 may be grouped together so that a singleURL may be used to perform health checks on multiple computing resources110. In this example, group user interface (UI) 214 is provided. Thegroup UI 214 is configured to receive a selection input. Once selected,the group UI 214 allows a user to select one or more of the URLs 206 A-Dto be selected for grouping. For example, once the group UI 214 receivesa selection input, a user may select the URLs 206A, 206B, and 206C to begrouped together. Once grouped, a group uniform resource locator (URL)206E is generated. The URL 206E is indicated as a grouping for computingresources 110A, 110B, and 110N. If the group URL 206E is selected, whenreceived by the parallel executor server 114, the parallel executorserver 114 determines the URLs of the computing resources 110 associatedwith URL 206E. Thus, in lieu of selecting individual URLs, the user canselect a group. The parallel executor server 114 transmits a healthcheck command code to the computing resources 110A-N associated with theURL 206E. Once the health check information is received from thecomputing resources 110A-N, the health check information is provided tothe UE 102 and rendered in the health check status user interface 212.

FIG. 3 is an illustrative process 300 for establishing identifiers toprovide clustered health checks, in accordance with some examples of thepresent disclosure. The process and other processes described herein areillustrated as example flow graphs, each operation of which mayrepresent a sequence of operations that can be implemented in hardware,software, or a combination thereof. In the context of software, theoperations represent computer-executable instructions stored on one ormore computer-readable storage media that, when executed by one or moreprocessors, perform the recited operations. Generally,computer-executable instructions include routines, programs, objects,components, data structures, and the like that perform particularfunctions or implement particular abstract data types. The order inwhich the operations are described is not intended to be construed as alimitation, and any number of the described operations can be combinedin any order and/or in parallel to implement the processes.

Referring to FIG. 3, the process 300 commences at operation 302, wherethe application 106 to be checked is identified. The presently disclosedsubject matter is not limited to any particular type of application forthe application 106. For example, the application 106 can be, but is notlimited to, a locally-run application (i.e. where the applicationoperates completely on the user equipment 108), an application hosted ona remote service, or various combinations thereof.

The process 300 continues to operation 304, where the computingresources 110 necessary to operate or provide services for theapplication are identified. The presently disclosed subject matter isnot limited to any particular type of the computing resources 110. Forexample, the computing resources 110 can be, but are not limited to,servers, nodes, data stores, network services, and the like.

The process 300 continues to operation 306, where uniform resourcelocators (URLs) are received for the computing resources 110 identifiedin operation 304. Although URLs are used in process 300, the use of URLsis merely exemplary, as other types of identifiers may be used. As usedherein, an identifier is an address or location to which the computingresources 110 can be individually identified and communicated with.

The process 300 continues to operation 308, where the URLs areassociated with health check commands. In this manner, when a URL isentered, the URL is combined with a command that, when received, causesthe performance of a health check and the transmission of the healthcheck to the querying entity. In this manner, the input of an identifier(in these examples, the URLs) automatically invokes a command to performa health check. Therefore, the transmission is a combination of theidentifier to locate and communicate with the particular computingresource 110, as well as, a command to perform a health check andtransmit the results to the querying unit. The URLs (or otheridentifiers) along with their associated health check command stringsmay be stored in the data store 112 or other accessible data store. Insome examples, the URLs (or other identifiers) along with theirassociated health check command strings may be stored in other locales,such as the user equipment 102.

The process 300 continues to operation 310, where the URLs are providedto the health check application 104. As noted above, other types ofidentifiers may be provided.

The process 300 continues to operation 402 of process 400, described inmore detail in FIG. 4, below.

FIG. 4 is an illustrative process 400 for using the health checkapplication 104, in accordance with some examples of the presentdisclosure.

The process 400 commences at operation 402, where the URLs of process300 are received at the user equipment 102 executing the health checkapplication 104. The URLs may be provided upon a query from the healthcheck application 104 or as part of a process, such as when theapplication 106 is undergoing development. For example, a notificationmay be received at the user equipment 102 that there may be issues withthe application 106, such as lag or data issues.

A user operating user equipment 102 may receive an identification thatthe application 106 is not operating optimally. The user may select a“GET URLs” input for the application 106. The health check application104, after receiving the “GET URLs” input, queries the parallel executorserver 114. The parallel executor server 114 queries the data store 112for the URLs and the health check commands for the computing resources110 associated with the application 106. The information is passed tothe health check application 104. In some examples, the parallelexecutor server 114 may execute a health check operation upon thereceipt of a notification that the application 106 is not runningoptimally without requiring an input such as the selection of the URLs206 or other input from a user. In some examples, the notification mayinclude which of the computing resources 110 are not running optimally,and therefore, the health check operation may be performed just on theparticular computing resource rather than all computing resources 110.

The process 400 continues to operation 404, where bookmarks to beprovided in a bookmarks bar 208 are generated for the URLs received. Itshould be noted that the presently disclosed subject matter is notlimited to the rendering of the URLs 206 in bookmark format, as othertypes of formats may be used, including selectable links, lists, and thelike. Further, the URLs may be received at other points in the operationof the health check application 104. For example, the health checkapplication 104 may query for and receive the URLs 206 before anynotification of issues, at various stages of development of theapplication 106, or any other time in which the computing resources 110have been, or are being, identified.

The process 400 continues to operation 406, where an input of one of theURLs 206 is received. In some examples, the URLs 206 may be grouped orotherwise segregated. In this matter, the input may be for theparticular grouping of URLs 206 rather than a single URL 206.

The process 400 continues to operation 408, where the URLs aretransmitted to the parallel executor server 114.

The process 400 continues to operation 502 of process 500.

FIG. 5 is an illustrative process 500 for executing a health checkcommand by the parallel executor server 114, in accordance with someexamples of the present disclosure.

The process 500 commences at operation 502, where the URLs that aretransmitted pursuant to operation 408 of the process 400 are received bythe parallel executor server 114.

The process 500 continues to operation 504, where the parallel executorserver 114 transmits a health check command code to the computingresources 110 associated with the URL 206 that were receive at operation502.

The process 500 continues to operation 506, where the health checkinformation is received at the parallel executor server 114 for thequeried computing resources 110.

The process continues to operation 508, where the health checkinformation is transmitted to the health check application 104.

The process 500 continues to operation 412 of process 400, where thehealth check information is received at the health check application104. The health check information may be rendered in a user interfacefor reference. The process 400 thereafter ends, thus ending processes300 and 500.

FIG. 6 depicts a component level view of the UE 102 for use with thesystems and methods described herein. The UE 102 could be any UE capableof making audio and/or video calls on a cellular network, an internetmultimedia subsystem, and/or an IP network. For clarity, the UE 102 isdescribed herein generally as a cell phone, smart phone, or laptopcomputer. One of skill in the art will recognize, however, that thesystems and methods described herein can also be used with a variety ofother electronic devices, such as, for example, tablet computers,desktops, and other network connected devices. Indeed, the UE 102 can beany device that can send and receive video calls, audio calls, and/ormessaging that can benefit from improved call management.

The UE 102 can comprise several components to execute theabove-mentioned functions. As discussed below, the UE 102 can comprisememory 602 including an operating system (OS) 604 and one or morestandard applications 606. The standard applications 606 can includemany features common to UEs such as, for example, calendars, call logs,voicemail, etc. In this case, the standard applications 606 can alsocomprise a video call application, an audio call application, and amessaging application to enable users to engage in audio calls, videocalls, and messaging, among other things. The standard applications 606can also include contacts to enable the user to select a contact toinitiate, for example, a video call, audio call, text message, etc.

The UE 102 can also comprise the health check application 104. Asmentioned above, the health check application 104 can be used toreceive, select, and group URLs of the computing resources 110associated with the application 106. The health check application 104communicates with a parallel executor server 114 to request and receivehealth check information.

The UE 102 can also comprise one or more processors 612 and one or moreof removable storage 614, non-removable storage 616, transceiver(s) 618,output device(s) 620, and input device(s) 622. In some examples, such asfor cellular communication devices, the UE 102 can also include a SIM624 and/or an embedded SIM (eSIM) 626, which can include a mobilecountry code (MCC), mobile network code (MNC), international mobilesubscriber identity (IMSI), cellular phone number, and other relevantinformation. In some examples, one or more of the functions of thehealth check application 104 can be stored on the SIM 624 or the eSIM626 in addition to, or instead of, being stored in the memory 602.

In various implementations, the memory 602 can be volatile (such asrandom access memory (RAM)), non-volatile (such as read only memory(ROM), flash memory, etc.), or some combination of the two. The memory602 can include all, or part, of the health check application 104 or aURL listing, among other things. In some examples, rather than beingstored in the memory 602, some, or all, of the health check application104, and other information (e.g., a listing of URLs) can be stored on aremote server or a cloud of servers accessible by the UE 102.

The memory 602 can also include the OS 604. Of course, the OS 604 variesdepending on the manufacturer of the UE 102. The OS 604 contains themodules and software that support a UE's basic functions, such asscheduling tasks, executing applications, and controlling peripherals.In some examples, the OS 604 can enable the health check application104, and provide other functions, as described above, via thetransceiver(s) 618. The OS 604 can send information to a graphical userinterface (GUI) (not shown), for example, to cause the GUI to displaythe URLs 206 in the bookmarks bar 208. The OS 604 can also receiveinputs from the GUI to cause the UE 102 to use the standard applications606 for some functions, while other functions are handled in the healthcheck application 104, among other things. The OS 604 can also enablethe UE 102 to send and retrieve other data and perform other functions.

The UE 102 can also comprise one or more processors 612. In someimplementations, the processor(s) 612 can be a central processing unit(CPU), a graphics processing unit (GPU), both CPU and GPU, or any otherprocessing unit. The UE 102 may also include additional data storagedevices (removable and/or non-removable) such as, for example, magneticdisks, optical disks, or tape. Such additional storage is illustrated inFIG. 6 by removable storage 614 and non-removable storage 616.

Non-transitory computer-readable media may include volatile andnonvolatile, removable and non-removable tangible, physical mediaimplemented in technology for storage of information, such as computerreadable instructions, data structures, program modules, or other data.The memory 602, removable storage 614, and non-removable storage 616 areall examples of non-transitory computer-readable media. Non-transitorycomputer-readable media include, but are not limited to, RAM, ROM,electronically erasable programmable ROM (EEPROM), flash memory or othermemory technology, compact disc ROM (CD-ROM), digital versatile discs(DVD) or other optical storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othertangible, physical medium which can be used to store the desiredinformation and which can be accessed by the UE 102. Any suchnon-transitory computer-readable media may be part of the UE 102 or maybe a separate database, databank, remote server, or cloud-based server.

In some implementations, the transceiver(s) 618 include any transceiversknown in the art. In some examples, the transceiver(s) 618 can includewireless modem(s) to facilitate wireless connectivity with othercomponents (e.g., between the UE 102), the Internet, and/or an intranet.Specifically, the transceiver(s) 618 can include one or moretransceivers that can enable the UE 102 to send and receive video calls,audio calls, and messages and to perform other functions. Thus, thetransceiver(s) 618 can include multiple single-channel transceivers or amulti-frequency, multi-channel transceiver to enable the UE 102 to sendand receive video calls, audio calls, messaging, etc. The transceiver(s)618 can enable the UE 102 to connect to multiple networks including, butnot limited to the 2G, 3G, 4G, 5G, and Wi-Fi networks. Thetransceiver(s) can also include one or more transceivers to enable theUE 102 to connect to future (e.g., 6G) networks, Internet-of-Things(IoT), machine-to machine (M2M), and other current and future networks.

The transceiver(s) 618 may also include one or more radio transceiversthat perform the function of transmitting and receiving radio frequencycommunications via an antenna (e.g., Wi-Fi or Bluetooth®). In otherexamples, the transceiver(s) 618 may include wired communicationcomponents, such as a wired modem or Ethernet port, for communicatingvia one or more wired networks. The transceiver(s) 818 can enable the UE102 to make audio and video calls, download files, access webapplications, and provide other communications associated with thesystems and methods, described above.

In some implementations, the output device(s) 620 include any outputdevices known in the art, such as a display (e.g., a liquid crystal orthin-film transistor (TFT) display), a touchscreen, speakers, avibrating mechanism, or a tactile feedback mechanism. Thus, the outputdevice(s) can include a screen, or display, on which the GUI can bedisplayed. The output device(s) 620 can also include speakers, orsimilar devices, to play sounds or ringtones when an audio call or videocall is received. Output device(s) 620 can also include ports for one ormore peripheral devices, such as headphones, peripheral speakers, or aperipheral display.

In various implementations, input device(s) 622 include any inputdevices known in the art. For example, the input device(s) 622 mayinclude a camera, a microphone, or a keyboard/keypad. The inputdevice(s) 622 can include a touch-sensitive display or a keyboard toenable users to enter data and make requests and receive responses viaweb applications (e.g., in a web browser), make audio and video calls,and use the standard applications 606, among other things. Thetouch-sensitive display or keyboard/keypad may be a standard push buttonalphanumeric multi-key keyboard (such as a conventional QWERTYkeyboard), virtual controls on a touchscreen, or one or more other typesof keys or buttons, and may also include a joystick, wheel, and/ordesignated navigation buttons, or the like. A touch sensitive displaycan be used to display the GUI, for example, and to act as both an inputdevice 622 and an output device 620.

The presently disclosed examples are considered in all respects to beillustrative and not restrictive. The scope of the disclosure isindicated by the appended claims, rather than the foregoing description,and all changes that come within the meaning and range of equivalentsthereof are intended to be embraced therein.

What is claimed is:
 1. A method comprising: receiving, at a parallelexecutor server, a first identifier associated with a first computingresource used in conjunction with an execution of an application and asecond identifier associated with a second computing resource used inconjunction with the execution of the application; generating a firsthealth check command code for the first computing resource and a secondhealth check command code for the second computing resource, the firsthealth check command code including a first request for a first responseof first health check information from the first computing resource andthe second health check command code including a second request for asecond response of second health check information from the secondcomputing resource; generating a first link comprising the firstidentifier and the first health check command code; and generating asecond link comprising the second identifier and the second health checkcommand code, wherein selecting the first link or the second link causesthe parallel executor server to execute the first health check commandcode and the second health check command code.
 2. The method of claim 1,further comprising: receiving a selection of the first link from a userequipment; connecting with the first computing resource using the firstidentifier associated with the first link; transmitting the first healthcheck command code to the first computing resource; receiving the firsthealth check information from the first computing resource; andtransmitting the first health check information to the user equipment.3. The method of claim 1, further comprising: receiving, from a userequipment, a first selection of the first link and a second selection ofthe second link; connecting with the first computing resource using thefirst identifier associated with the first link and the second computingresource using the second identifier associated with the second link;transmitting the first health check command code to the first computingresource and the second health check command code to the secondcomputing resource; receiving the first health check information and thesecond health check information; and transmitting the first health checkinformation and the second health check information to the userequipment.
 4. The method of claim 1, wherein the first link or thesecond link is a uniform resource locator (URL), an Internet Protocoladdress, or a node address.
 5. The method of claim 1, furthercomprising: receiving a notification that the first computing resourcehas failed to meet a performance threshold; identifying the first linkassociated with the first computing resource; transmitting the firsthealth check command code to the first computing resource; receiving thefirst health check information; and transmitting the first health checkinformation to a user equipment associated with maintenance of the firstcomputing resource.
 6. The method of claim 1, further comprising:receiving a notification that the application has failed to meet aperformance threshold; identifying the first computing resource and thesecond computing resource associated with the application; retrievingthe first health check command code to the first computing resource andthe second health check command code to the second computing resource;identifying the first link associated with the first computing resourceand the second link associated with the second computing resource;transmitting the first health check command code to the first computingresource using the first link and the second health check command codeto the second computing resource using the second link; receiving thefirst health check information and the second health check information;and transmitting the first health check information and the secondhealth check information to a user equipment associated with maintenanceof the application.
 7. The method of claim 1, further comprising:transmitting the first link and the second link to a user equipmentrequesting the first link and the second link.
 8. A system comprising:one or more processors; and one or more non-transitory computer-readablemedia storing instructions executable by the one or more processors,wherein the instructions, when executed, cause the system to performoperations comprising: receiving, at a parallel executor server, a firstidentifier associated with a first computing resource used inconjunction with an execution of an application and a second identifierassociated with a second computing resource used in conjunction with theexecution of the application; generating a first health check commandcode for the first computing resource and a second health check commandcode for the second computing resource, the first health check commandcode including a first request for a first response of first healthcheck information from the first computing resource and the secondhealth check command code including a second request for a secondresponse of second health check information from the second computingresource; generating a first link comprising the first identifier andthe first health check command code; and generating a second linkcomprising the second identifier and the second health check commandcode, wherein selecting the first link or the second link causes theparallel executor server to execute the first health check command codeand the second health check command code.
 9. The system of claim 8, theoperations further comprising: receiving a selection of the first linkfrom a user equipment; connecting with the first computing resourceusing the first identifier associated with the first link; transmittingthe first health check command code to the first computing resource;receiving the first health check information from the first computingresource; and transmitting the first health check information to theuser equipment.
 10. The system of claim 8, the operations furthercomprising: receiving, from a user equipment, a first selection of thefirst link and a second selection of the second link; connecting withthe first computing resource using the first identifier associated withthe first link and the second computing resource using the secondidentifier associated with the second link; transmitting the firsthealth check command code to the first computing resource and the secondhealth check command code to the second computing resource; receivingthe first health check information and the second health checkinformation; and transmitting the first health check information and thesecond health check information to the user equipment.
 11. The system ofclaim 8, wherein the first link or the second link is a uniform resourcelocator (URL), an Internet Protocol address, or a node address.
 12. Thesystem of claim 8, the operations further comprising: receiving anotification that the first computing resource has failed to meet aperformance threshold; identifying the first link associated with thefirst computing resource; transmitting the first health check commandcode to the first computing resource; receiving the first health checkinformation; and transmitting the first health check information to auser equipment associated with maintenance of the first computingresource.
 13. The system of claim 8, the operations further comprising:receiving a notification that the application has failed to meet aperformance threshold; identifying the first computing resource and thesecond computing resource associated with the application; retrievingthe first health check command code to the first computing resource andthe second health check command code to the second computing resource;identifying the first link associated with the first computing resourceand the second link associated with the second computing resource;transmitting the first health check command code to the first computingresource using the first link and the second health check command codeto the second computing resource using the second link; receiving thefirst health check information and the second health check information;and transmitting the first health check information and the secondhealth check information to a user equipment associated with maintenanceof the application.
 14. The system of claim 8, the operations furthercomprising: transmitting the first link and the second link to a userequipment requesting the first link and the second link.
 15. Anon-transitory computer-readable media storing computer-executableinstructions, which when executed by one or more processors, cause theone or more processors to perform operations comprising: receiving, at aparallel executor server, a first identifier associated with a firstcomputing resource used in conjunction with an execution of anapplication and a second identifier associated with a second computingresource used in conjunction with the execution of the application;generating a first health check command code for the first computingresource and a second health check command code for the second computingresource, the first health check command code including a first requestfor a first response of first health check information from the firstcomputing resource and the second health check command code including asecond request for a second response of second health check informationfrom the second computing resource; generating a first link comprisingthe first identifier and the first health check command code; andgenerating a second link comprising the second identifier and the secondhealth check command code, wherein selecting the first link or thesecond link causes the parallel executor server to execute the firsthealth check command code and the second health check command code. 16.The non-transitory computer-readable media of claim 15, the operationsfurther comprising: receiving a selection of the first link from a userequipment; connecting with the first computing resource using the firstidentifier associated with the first link; transmitting the first healthcheck command code to the first computing resource; receiving the firsthealth check information from the first computing resource; andtransmitting the first health check information to the user equipment.17. The non-transitory computer-readable media of claim 15, theoperations further comprising: receiving, from a user equipment, a firstselection of the first link and a second selection of the second link;connecting with the first computing resource using the first identifierassociated with the first link and the second computing resource usingthe second identifier associated with the second link; transmitting thefirst health check command code to the first computing resource and thesecond health check command code to the second computing resource;receiving the first health check information and the second health checkinformation; and transmitting the first health check information and thesecond health check information to the user equipment.
 18. Thenon-transitory computer-readable media of claim 15, wherein the firstlink or the second link is a uniform resource locator (URL), an InternetProtocol address, or a node address.
 19. The non-transitorycomputer-readable media of claim 15, the operations further comprising:receiving a notification that the first computing resource has failed tomeet a performance threshold; identifying the first link associated withthe first computing resource; transmitting the first health checkcommand code to the first computing resource; receiving the first healthcheck information; and transmitting the first health check informationto a user equipment associated with maintenance of the first computingresource.
 20. The non-transitory computer-readable media of claim 15,the operations further comprising: receiving a notification that theapplication has failed to meet a performance threshold; identifying thefirst computing resource and the second computing resource associatedwith the application; retrieving the first health check command code tothe first computing resource and the second health check command code tothe second computing resource; identifying the first link associatedwith the first computing resource and the second link associated withthe second computing resource; transmitting the first health checkcommand code to the first computing resource using the first link andthe second health check command code to the second computing resourceusing the second link; receiving the first health check information andthe second health check information; and transmitting the first healthcheck information and the second health check information to a userequipment associated with maintenance of the application.